🤖 fix: Handle emojis with variation selectors in status_set #468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes two issues with the
status_settool:1. Emoji Validation Failures
Problem: Emojis with variation selectors (like ✏️) were incorrectly rejected by validation.
Root Cause: The validator used
[...str].lengthto count characters, which counts code points. Emojis with variation selectors (U+FE0F) have 2 code points but represent a single grapheme cluster.Solution: Use
Intl.Segmenter(built-in API) to count grapheme clusters - what users perceive as single characters. This properly handles:Example:
2. Error Message Styling
Problem: Error messages in
StatusSetToolCallusedtext-smclass, making them smaller than surrounding text in the tool header.Solution: Removed
text-smclass so errors use the same font size as other header content.Generated with
cmux